into monthlyupdate

Co-authored-by: Divyesh-Khokhar <divyesh.k@ibm.com>
Co-authored-by: Raahithyaj <raahithya.jayaram@ibm.com>
Co-authored-by: amitpandey0217 <amit.pandey17@ibm.com>

…rets regardless of Slack config

The prepareUpdateSecrets() function in tekton.py was introduced in PR #425
("day2 fix for devops slack secret issue") which added an early return when
slack_token or slack_channel are not provided. This inadvertently placed the
pipeline-db2-license secret creation after the early return, meaning the
secret was never created for users who do not have Slack configured.

The PipelineRun template (pipelinerun-update.yml.j2) unconditionally binds
the shared-db2 workspace to secretName: pipeline-db2-license. When the
secret does not exist, the update-db2 task pod is stuck in Init:0/2 with
repeated FailedMount errors, blocking the entire mas-update pipeline run.

Fix: move pipeline-db2-license secret creation before the Slack guard so it
is always created regardless of whether Slack credentials are provided.